Skip to content

docs: FEATURE-GATES -> CONFIG-OPTIONS #827

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 13, 2025

Conversation

beraldoleal
Copy link
Member

Following community discussions, there's a desire to clarify the distinction between feature gates and config options. This update aligns the documentation with our intended direction for upcoming releases and avoids ambiguity.

Note: Some internal structs still use the old terminology and are not updated in this commit. We plan to address those separately.

- Description for the changelog

We are updating our feature gates definition and from now on we are using the "config options" terminology. This will not change how users enable/disable features for this release, so probably we should not mention this change in the changelog.

Following community discussions, there's a desire to clarify the
distinction between feature gates and config options. This update aligns
the documentation with our intended direction for upcoming releases and
avoids ambiguity.

Note: Some internal structs still use the old terminology and are not
updated in this commit. We plan to address those separately.

Signed-off-by: Beraldo Leal <[email protected]>
@openshift-ci openshift-ci bot requested review from snir911 and vvoronko July 24, 2025 15:51
@beraldoleal beraldoleal requested review from gkurz and bpradipt July 24, 2025 16:15
Copy link

openshift-ci bot commented Jul 24, 2025

@beraldoleal: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link
Contributor

@bpradipt bpradipt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 31, 2025
Copy link
Member

@gkurz gkurz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Thanks @beraldoleal !

@beraldoleal
Copy link
Member Author

@littlejawa, I tried to re-trigger the failing check, but not working. Safe to ignore since is not required?

@littlejawa
Copy link
Contributor

The error is about the dm-verity image. From what I can see in the log, the bundle in your branch references a pretty old version of it. That's why it's failing.
You would probably have it passing if your rebase.

Now since you're just changing docs, I don't think it's worth running through another full rebuild/testing (the prow tests take forever :-( ).
Let's ignore it.

@beraldoleal beraldoleal merged commit d77c979 into openshift:devel Aug 13, 2025
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants